The coding standard for the "ee" editor.
        
This is to help maintainers stay with the existing style, if they wish.

Most of the generally accepted principles for source code are not repeated here.
An example would be to make each function have a simple purpose, that is
easily understood by a person.

We will try to carry out the design goal for readability.

For the naming convention, we separate words in a phrase with undescores, e.g.,
"the_number_of_characters".  Since that is closer to the corresponding English
text, "the number of characters", than, e.g., "TheNumberOfCharacters", our
convention seems easier to read.  Readability is also considered in file names,
e.g., "coding standard.txt" rather than "CodingStandard.txt" .

Class names end in "_class" .  Data members are prefised with "m_" .

There is usually only one class in each header file, and only one in each
.cpp  file.  But if classes are tightly bound together, then they can be
in the same source files.  An example is the list of windows.  A class for
a single window is closely related, so they are declared together.

In a header file, the public and protected members of a class are declared
before the private members.  In a .cpp file, the code is in bottom-up order.
If a method "a" is called by a method "b", then "a" is defined first.  That
can result in a private method being defined before a public one.  If the 
"bottom-up" rule doesn't determine the order of two functions, then they
appear in the same order as in the header file.